Skip to content

PS-11205 fix: When fs_buffer_directory is not set the temporary buffer directory is created in the current binary path rather than in /tmp#135

Merged
percona-ysorokin merged 1 commit into
Percona-Lab:0.2from
percona-ysorokin:empty_fs_buffer_directory_fix
May 27, 2026
Merged

PS-11205 fix: When fs_buffer_directory is not set the temporary buffer directory is created in the current binary path rather than in /tmp#135
percona-ysorokin merged 1 commit into
Percona-Lab:0.2from
percona-ysorokin:empty_fs_buffer_directory_fix

Conversation

@percona-ysorokin
Copy link
Copy Markdown
Collaborator

https://perconadev.atlassian.net/browse/PS-11205

  • Default buffer directory for S3 storage backend is now a unique subdirectory under the OS temp directory (e.g. /tmp on Linux) if '<storage.fs_buffer_directory>' configuration parameter is not set.
  • Auto-created temp directory is removed on storage backend destruction; user-provided directories are never deleted.
  • Updated README to document new behavior.

…r directory is created in the current binary path rather than in /tmp

https://perconadev.atlassian.net/browse/PS-11205

* Default buffer directory for S3 storage backend is now a unique subdirectory
under the OS temp directory (e.g. /tmp on Linux) if '<storage.fs_buffer_directory>'
configuration parameter is not set.
* Auto-created temp directory is removed on storage backend destruction;
  user-provided directories are never deleted.
* Updated README to document new behavior.
@kamil-holubicki
Copy link
Copy Markdown
Collaborator

Maybe add some test?

@percona-ysorokin percona-ysorokin merged commit 4d3ebb5 into Percona-Lab:0.2 May 27, 2026
7 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants